Systems and methods for remote ATM access

ABSTRACT

A system includes a location identifier device configured to receive location information from a user device; a surveillance device configured to capture video surveillance; and a computer system. The computer system is configured to: receive the location information; receive a request for an ATM transaction that includes attribute information associated with the user; obtain, from the received video surveillance, captured attribute information associated with the user; determine that the captured attribute information at least partially matches the received attribute information; transmit a transaction code to the user device based on (i) the location information from the user device being within the area, (ii) the captured attribute information at least partially matching the attribute information, and (iii) the identification of the user associated with the request; and facilitate the ATM transaction based at least partially on the received transaction code.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/377,311 entitled “SYSTEMS AND METHODS FOR REMOTE ATM ACCESS,” filed Dec. 13, 2016, which claims the benefit of and priority to U.S. Provisional Patent Application No. 62/317,322 entitled “SYSTEMS AND METHODS FOR REMOTE ATM ACCESS”, filed Apr. 1, 2016, each of which are incorporated herein by reference in their entireties.

BACKGROUND

Generally, when a user wishes to complete a transaction, such as withdrawing funds from an automated teller machine (ATM), the user first has to authenticate himself to the ATM. To do so, the user presents their debit card by inserting the debit card into a card reader or by tapping their phone to transmit a token associated with that debit card. The user then enters an account personal identification number (PIN) at the ATM. At drive-through ATMs, this task may be particularly cumbersome. For example, the user may have to open his car window during the cold or rain to manually insert the debit card or tap his phone and to manually enter the PIN at the ATM. This manual activity presents problems. For example, the user may accidentally drop and damage the smartphone while attempting to tap the phone at the ATM. As another example, by opening the window of his car to access the ATM, the user may expose himself to bad weather (e.g., rain, extreme cold, extreme heat, etc.) for prolonged periods of time.

SUMMARY

One embodiment relates to banking system configured to remotely initiating a transaction at an ATM. The banking system includes a location identifier device configured to at least one of transmit or receive location information, and a computer system comprising a processor and a memory, the computer system configured to: receive location information associated with a user device, determine the location information associated with the user device matches a location configured for pre-staging an ATM transaction, transmit an ATM pre-stage authorization signal to the user device, transmit an authentication decision to the user device, and transmit a transaction code to the user device.

One embodiment relates to a method for remotely initiating a transaction at an ATM. The method includes transmitting, via a user device, location information to a financial institution computing system associated with an ATM, enabling, via the user device, an ATM pre-stage feature responsive to receipt of an ATM pre-stage authorization signal, receiving, via user input, user authentication information responsive to enabling the ATM pre-stage feature, and transmitting, via the user device, transaction information to the financial institution computing system.

These and other features, together with the organization and manner of operation thereof, will become apparent from the following detailed description when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a computing system for a financial institution according to an example embodiment.

FIG. 2 is a block diagram of the user device according to an example embodiment.

FIG. 3 is a block diagram of a location identifier device according to an example embodiment

FIG. 4 is an overhead view of a bank branch according to an example embodiment.

FIG. 5 is a flow diagram of a method of remotely initiating an ATM transaction based according to an example embodiment.

DETAILED DESCRIPTION

Referring to the figures generally, systems and methods of remotely initiating an ATM transaction are described. As a customer approaches an ATM, the ATM (or underlying backend computer system) determines that the customer is approaching the ATM and may want to initiate an ATM transaction based on a determined proximity of the customer to the ATM. For example, if the customer is waiting in line at a drive-up ATM, the system can determine that the customer is approaching the ATM (e.g., based on a user device being in proximity to a location beacon, based on location information provided from the user device to the system, etc.). Accordingly, the system can trigger a user device (e.g., a smartphone, a car infotainment system, a tablet, etc.) to display a user interface that allows the customer to remotely initiate an ATM transaction that can be finalized at the ATM. As a result, the customer spends less time at the ATM which, in turn, reduces wait times at the ATM and increases the number of customer transactions that the ATM can process in a given amount of time.

Referring to FIG. 1 , a block diagram of a computing system 100 for a financial institution 102 is shown according to an example embodiment. Generally, the financial institution 102 provides financial services (e.g., demand deposit accounts, credit accounts, etc.) to a plurality of customers. The financial institution 102 includes a financial institution (“FI” in FIG. 1 ) computing system 104 and an ATM network having a plurality of ATMs 106. The ATMs are located at a plurality of physical locations that can be visited by customers (e.g., bank branches, malls, airports, stores, drive-through banking centers, bars, restaurants, offices, etc.). The financial institution 102 provides banking services to the customers via the ATMs 106. For example, customers can authenticate themselves at a given ATM 106 and deposit funds into accounts, withdraw funds from accounts, transfer funds between accounts, view account balances, and the like. As described in further detail below, the financial institution 102 allows a customer to remotely initiate a transaction at an ATM 106 when the customer is determined to be in proximity to the ATM 106 for later completion at the ATM 106.

The financial institution computing system 104 is a backend computer system that supports the ATMs 106 and other financial services offered by the financial institution. Accordingly, the financial institution computing system 104 includes a network interface 108, an account management circuit 110, an ATM transaction circuit 112, an account database 114, and an ATM database 116. The network interface 108 is structured to facilitate data communication with other computing devices (e.g., ATMs 106, user devices 120, etc.) directly or via a network (e.g., network 122, a private internal network associated with the financial institution 102, etc.). The network interface 108 may communicate over any of a variety of network protocols, including Ethernet, Bluetooth, WiFi, and the like. The account management circuit 110 is structured to maintain accounts associated with customers of the financial institution 102 and to facilitate transactions associated with the accounts. The ATM transaction circuit 112 is structured to facilitate customer transactions via the ATMs 106. As described in further detail below, the ATM transaction circuit 112 also interfaces with customer devices 120 to facilitate remote ATM transaction initiation and completion. The account database 114 stores customer account information, including account numbers, account balances, customer contact information, customer preferences, and other account information. The ATM database 116 stores information relating to the ATMs 106, such as ATM location information, ATM capability information, ATM service information, and the like.

The financial institution 102 includes a plurality of ATMs 106. In some arrangements, the ATMs 106 may have different capabilities. For example, a first ATM may be able to both dispense cash for withdrawals and receive cash for deposits, while a second ATM may not have the capability to receive cash for deposits. Each of the ATMs 106 communicates with the financial institution computing system 104 via the network 122 or an internal private network. The ATMs 106 are used by customers of the financial institution 102 to receive financial services and to perform financial transactions. In some arrangements, the ATMs 106 can communicate with user devices 120 to execute transactions via wireless communication protocols, such as WiFi, Bluetooth, near field communication (NFC), and the like. For example, a customer can tap a properly configured user device 120 at an ATM 106 to transmit a payment card token associated with the customer's debit card via NFC to the ATM 106 thereby eliminating the need for the customer to dip his credit card into a reader of the ATM 106.

In some arrangements, each of the ATMs 106 is associated with a locator beacon 118. In other arrangements, a grouping of ATMs 106 is associated with at least one locator beacon 118. In further arrangements, a locator beacon 118 can be associated with an area near an ATM 106. The locator beacon 118 may be positioned on, inside of, or in the vicinity of a given ATM 106. Each locator beacon 118 broadcasts a unique beacon identifier within a limited range of the beacon. In some arrangements, the locator beacons 118 are Bluetooth® Low Energy beacons (e.g., iBeacons®). In other arrangements, the locator beacons 118 are wireless network transmitters or access points, and the unique beacon identifier is a wireless network SSID. The limited range of the beacon may have a maximum broadcast range of approximately 10 meters. The maximum broadcast range may be increased or decreased by respectively increasing or decreasing the broadcast power of each beacon. In some arrangements, a plurality of beacons can be used to geo-fence a large area, a plurality of beacons that designate sub-areas within a single area, such as individual drive-through lanes, etc.). In some arrangements, location identifier devices 118 can be associated with other items or areas, such as the drive-up lane that guides vehicles to a drive-up ATM.

Each of the locator beacons 118 geo-fences the associated location by broadcasting the unique identifier such that a location aware device (e.g., the user device 120) can determine that it is in a certain location based on the received unique identifier. As described in further detail below, when a customer brings a user device 120 capable of receiving signals from the locator beacons 114, an interface of an application being executed on the user device 120 can be changed to allow the customer to initiate a transaction with an associated ATM before the customer is authenticated at the ATM. In some arrangements, the associations of unique identifiers and ATMs is maintained by the financial institution computing system 102 in the ATM database 116. Each entry in the database includes a beacon identifier (e.g., a serial number that is broadcast from the beacon, an SSID, etc.) and an associated ATM identifier (e.g., a unique identifier that identifies a specific ATM 106 or a grouping of ATMs 106 in a specific location).

Still referring to FIG. 1 , customers of the financial institution 102 can access the various services provided by the financial institution 102 through user devices 120. The user devices 120 include personal computing devices such as laptops, PDAs, portable media devices, smartphones, tablet computing devices, wearable computing devices (e.g., a smartwatch, smart optical wear, etc.), vehicle infotainment systems (e.g., a computing device mounted inside of a vehicle and that includes a display and user input to present vehicle information, entertainment media, applications, navigation information and the like to passengers of a vehicle), etc. that may access one or more programs, servers, networks, central computers, etc. The user devices 120 communicate with the financial institution computing system 104 of the financial institution 102 through the network 122. In some arrangements, the network 110 includes the internet. The user devices 120 may execute a financial institution application associated with the financial institution 102. In some arrangements, the application is executed locally on the user device 120 (e.g., a smartphone application, a vehicle infotainment device application). In other arrangements, the application is accessed on the user device 120 via a website of the financial institution 12 maintained by the financial institution computing system 104 or otherwise accessible by the user device 120. Via the application, the customer can access various information about his or her accounts with the financial institution 102 (e.g., balances, interest rates, etc.), pay bills, view ATM and branch locations, and view additional services offered by the financial institution 102. For example, the customer may be able to remotely initiate (e.g., pre-stage) a transaction for execution by a nearby ATM 106 through an ATM pre-stage interface of the application as described in further detail below.

Referring to FIG. 2 , a block diagram of the user device 120 is shown according to an example embodiment. As discussed above, the user device 120 may be laptops, PDAs, portable media devices, smartphones, tablet computing devices, wearable computing devices (e.g., a smartwatch, smart optical wear, etc.), vehicle infotainment systems (e.g., a computing device mounted inside a vehicle and that includes a display and user input to present vehicle information, entertainment media, applications, navigation information and the like to passengers of a vehicle), etc. The user device 120 includes a network interface 202. The network interface 202 is a wireless network interface. The wireless network interface 202 includes any of a cellular transceiver (e.g., CDMA, GSM, LTE, etc.), a wireless network transceiver (e.g., 802.11X, ZigBee, Bluetooth, etc.), or a combination thereof (e.g., both a cellular transceiver and a Bluetooth transceiver). The network interface 202 is capable of receiving radio frequency transmissions from the locator beacons 118. Additionally, the network interface 202 is capable of communicating with the financial institution computing system 104 via the network 122 (e.g., via any combination of the Internet, cellular networks, personal area networks, Wifi networks, etc.).

The user device 120 includes a display 204 and a user input/output 206. In some arrangements, the display 204 and the user input/output 206 are combined (e.g., as a touchscreen display device). In other arrangements, the display 204 and the user input/output 206 are discrete devices. The user input/output 206 includes any of speakers, keyboards, notification LEDs, microphones, biometric sensors (e.g., fingerprint scanners), buttons, switches, cameras, or a combination thereof. In arrangements where the user device 120 is a vehicle infotainment system, the display 204 may be part of or integrated into the vehicle's dashboard.

In some arrangements, the user device 120 includes a location sensor 208. The location sensor 208 may be used to supplement location information determined based on the received position data. The location sensor 208 may be, for example, a GPS receiver, a GLONASS receiver, or the like.

The user device 120 includes a power source 212. The power source 212 may include grid power, battery power (e.g., alkaline batteries, rechargeable batteries, etc.), and/or another energy source. In arrangements where the power source 212 is a rechargeable battery, the user device 120 also includes circuitry configured to recharge the battery. In arrangements where the user device 120 is a vehicle infotainment system, the power source 212 may include a vehicle battery and/or an internal combustion engine that turns an alternator to generate electric power.

The functionality of the mobile device 120 described herein is controlled at least in part by the mobile banking circuit 214 and the ATM transaction circuit 216. Both the mobile banking circuit 214 and the ATM transaction circuit 216 are formed at least in part by the financial institution application associated with the financial institution 102. The mobile banking circuit 214 is structured to allow a customer of the financial institution 102 to manage accounts held with the financial institution via the mobile device 120 (e.g., to view balances, transfer funds, open accounts, close accounts, change contact information, etc.). The ATM transaction circuit 216 is structured to allow a customer to identify ATMs in the vicinity of to the customer (e.g., within a threshold distance, within a given locator beacon 118 broadcast range, etc.), make the customer's presence known to the identified ATM, and initiate a transaction remote from the identified ATM for completion at a later point in time. In some arrangements, the ATM transaction circuit is integrated into the mobile banking circuit 206.

Referring to FIG. 3 , a block diagram of a locator beacon 118 is shown according to an example embodiment. The locator beacon 118 includes a processor 302 and memory 304. The memory 304 may include any combination of RAM, ROM, NVRAM, or the like as described herein below. The locator beacon 118 includes a radio frequency data transmitter 306. The transmitter 306 may be a Bluetooth® transmitter 306. In some arrangements, the locator beacon 118 is a two-way device and includes a receiver 308 capable of receiving radio frequency data transmissions. In such arrangements, the transmitter 306 and the receiver 308 may take the form of a transceiver capable of sending and receiving radio frequency data transmissions. The locator beacon 118 includes a power source 312. The power source 310 may include any combination of grid power and battery power (e.g., alkaline batteries, rechargeable batteries, etc.).

Referring to FIG. 4 , an overhead view of a bank branch 400 is shown according to an example embodiment. The bank branch 400 may be the physical location of the financial institution 102. The bank branch 400 includes a plurality of different customer areas, including an ATM area 402 having a plurality of walk-up ATMs 106, and a drive-through area 404 having a plurality of drive-up ATMs 106. Each customer area is geo-fenced with at least one locator beacon 118. Each of the locator beacons 118 has a broadcast radius R defining a broadcast zone 406. The broadcast zone 406 of each of the locator beacons 118 may be varied in size of the broadcast radius R (e.g., by varying the broadcast power of each locator beacon 118) and in shape (e.g., by using signal shaping shields). In some arrangements, the broadcast radii R of multiple locator beacons 118 overlap (e.g., as shown in the drive-through area 404 and in the ATM area 402). In other arrangements, the broadcast radii R of multiple locator beacons 118 do not overlap.

As described above, based on the received position data (e.g., unique beacon identifier, location information, etc.) provided to the financial institution computing system 104 by a customer's mobile device 120, the financial institution computing system 104 can transmit or enable an ATM pre-stage interface associated with the determined position that permits the customer to initiate an ATM transaction remote from a given ATM 106. The transaction may be pre-staged upon entry of the customer into the geo-fenced area. The location identifier device 118 may be placed outside and/or inside of the ATM area 402 to detect customers approaching the ATM area 402. To that end, as the customer enters the ATM area 402, the customer may wait in line due to the unavailability of an ATM. For example, each of the ATMs may be occupied by other customers. While a customer is in line waiting for an available ATM 106, the transaction may be pre-staged. In some embodiments, a customer may pre-stage a transaction while waiting in line for an available ATM 106, while other customers at the ATM 106 complete their respective pre-staged transactions. When an ATM 106 becomes available, the customer waiting in line may complete the pre-staged transaction.

In other examples, the transaction may be pre-staged upon entry of a vehicle (e.g., the vehicle 408A, 408B, 408C) into the geo-fenced area. FIG. 4 shows three different vehicles: 408A, 408B, 408C. The vehicle 408A has not yet entered the drive-through area 404; the vehicle 408B has entered the drive-through area 404; and the vehicle 408C is occupying an ATM 106 in the drive-through area 404. The locator beacon 118 may be placed in the driveway leading up to the drive-through area 404 to detect customers entering the drive-through area 404. The customers may be detected via the user device 120 associated with the customer and/or the vehicle. In some examples, the user device 120 may include an infotainment device (e.g., a device including a display, information, entertainment, media, applications, navigation, or a combination thereof) disposed in, for example, the vehicle 408B such that the financial institution computing system 102 transmits an ATM pre-stage interface to the infotainment device 120 before the vehicle 408B reaches the ATM 106. The infotainment device 120 may be disposed in or proximate to, for example, a dashboard, headrest, visor, etc. in the vehicle. While the customer associated with the vehicle 408B waits in the drive-through for an available ATM 106, the transaction may be pre-staged via the infotainment device 120. In some embodiments, the transaction may be pre-staged via the infotainment device 120 while the other customer associated with the vehicle 408C completes their respective pre-staged transaction. When an ATM 106 becomes available, the vehicle 408B may proceed to the available ATM 106 to complete the pre-staged transaction. The customer in the vehicle 408A may not have access to the ATM pre-stage interface because the vehicle 408A is not within an area geo-fenced by a locator beacon 118 associated with the drive-through area 404.

Referring to FIG. 5 , a flow diagram of a method 500 of remotely initiating an ATM transaction is described according to an example embodiment. The flow diagram details the interaction between a user device 120 (the left most column) and a financial institution computing system 104, and various devices associated with the financial institution 102 (e.g., an ATM 106 and locator beacons 118).

The method 500 begins when beacon identifiers are broadcast by the locator beacons 118 at 502. The locator beacons 118 are positioned at designated areas associated with ATMs 106 of the financial institution (e.g., in the lobby, in an ATM area, in a drive-through area, etc.). Each of the locator beacons 118 wirelessly broadcasts a unique beacon identifier (e.g., a serial number, an SSID, etc.) to a distance of a broadcast radius of the beacon. Each locator beacon 118 is associated with an area and geo-fences that area with the broadcasted identifier. Accordingly, if a device (e.g., the user device 120) receives a certain beacon identifier (or combination of beacon identifiers), the location of the device is known to be within the broadcast range of the beacon associated with the identifier. The user device 120 receives a beacon identifier at 504. When the user device 120 enters the broadcast area of a given locator beacon 118, the user device 120 receives the beacon identifier associated with the given locator beacon 118.

In some arrangements, in some arrangements, the user device 120 transmits location information determined independent from the locator beacons 118, such as GPS coordinates, cellular network triangulation information, or the like, to the financial institution computing system 104. In such arrangements, steps 502 and 504 may be skipped, and the non-beacon location information is provided directly from the user device 120 to the financial institution computing system 104 at 506 as described in further detail below.

The user device transmits location information to the financial institution computing system at 104 at 506. The location information is electronic information indicating a particular location of the user device 120. The transmission of the location information from the user device 120 to the financial institution computing system 104 may be facilitated via the mobile banking circuit 214 or the ATM transaction circuit 216. In some arrangements, the location information relates to a beacon identifier transmitted by a locator beacon 118. In such arrangements, receipt of the beacon identifier may automatically trigger the user device 120 to transmit the location information to the financial institution computing system 104. In other arrangements, the location information relates to location information determined by the user device 120 (e.g., GPS coordinates).

In arrangements where the user device 120 transmits location information determined independent from the locator beacons 118, such as GPS coordinates, cellular network triangulation information, or the like, to the financial institution computing system 104 may skip steps 502 through 506. In further arrangements, steps 502 and 504 may be skipped when the customer is recognized as being near an ATM 106 based on recognition of the customer or the customer's vehicle by a camera or security system associated with the financial institution 102. If the customer approaches the ATM 106, a camera associated with the financial institution 102 can perform facial recognition on the customer to identify the customer as being near the ATM 106. If the customer is driving a known vehicle through a drive-through ATM location, the camera associated with the financial institution 102 can identify the vehicle and the customer based on a vehicle attribute (e.g., license plate number, VIN, make/model of the vehicle, etc.). In such arrangements, steps 502 through 506 may be skipped in the method 500.

The financial institution computing system 104 receives the location information associated with the user device 120 at 508. The location information is used by the financial institution computing system 104 to determine the position of the user device 120. In arrangements where the location information is or relates to a beacon identifier, the financial institution computing system 104 cross-references the ATM database 116 to identify ATMs 106 in the vicinity of the user device 120. In arrangements where the location information relates to other location information (e.g., GPS coordinates), the financial institution computing system 104 can cross-reference the location of the user device against the known locations of the ATMs to determine whether the user and/or customer is within a predetermined range of a given ATM 106. The financial institution computing system 104 determines that the user device 120 matches a location authorized for prestaging an ATM transaction at 510. For example, the location of the user device may be within a threshold distance or a geo-fenced area of a given ATM 106.

Still referring to FIG. 5 , the method 500 continues at 512 when the financial institution computing system 104 transmits an ATM pre-stage authorization signal to the user device 120. The ATM pre-stage authorization signal authorizes an ATM pre-stage function of the mobile banking application associated with the financial institution 102 (e.g., activates the ATM transaction circuit 216 of the user device 120). In some arrangements, the ATM pre-stage authorization signal includes a user interface of a mobile banking application for display at the user device 120. The ATM pre-stage interface may be transmitted via the network 122 such as the Internet, cellular network, etc. When the user device 120 receives the user interface, the user device 120 can render the user interface if the user is properly authenticated. The user interface may relate to an interface that allows the user to remotely initiate or otherwise pre-stage an ATM transaction. Remotely initiating the ATM transaction may be done while the user waits in line in an ATM area, drive-through, etc. Based on receipt of the ATM pre-stage authorization signal, the user device 120 enables an ATM pre-stage feature at 514. As described above, the ATM pre-stage feature may be an existing feature of the mobile banking application that is activated by the ATM pre-stage authorization signal or a new feature (e.g., a new user interface) transmitted to the user device 120.

Prior to allowing a user of the user device 120 to initiate an ATM transaction, the user must be authenticated as an account holder. Accordingly, at 516, the user device 120 receives and transmits user authentication information to the financial institution computing system 104. As used herein, the term “user authentication information” refers to data indicative of the identity of a customer and/or user of the user device 120 that is requesting the initiation of an ATM transaction via the user device 120. The user device 120 receives the user authentication data via a user input provided by the user. The user authentication information includes any of a password, a PIN (personal identification number), a user ID, an answer to a verification question, a biometric (e.g., a picture of the user's face, a fingerprint, a voice sample, a retina scan, etc.), an identification of a security image, or a combination thereof. In some arrangements, the user's possession of the user device 120 may also serve as a factor in authenticating the user (e.g., because a device identifier stored on the user device 120 during installation of a mobile banking application and a device identifier establishes a device-binding of the user device 120 to the user). Hence, for example, a two-factor authentication may be achieved based on the user's possession of the user device 120 and entry of a password, PIN (e.g., a 4-digit pin), biometric, or any other previously listed authentication factor into the user device 120. The user authentication information is transmitted to the financial institution computing system 104 for verification.

The financial institution computing system 104 authenticates the user of the user device 120 at 518. The financial institution computing system 104 compares the received user authentication information with known and verified user authentication information. In some arrangements, the user may be authenticated prior to arriving in front of the ATM 106. Accordingly, the user may not be further authenticated when arriving at the ATM. In arrangements in which further authentication is not performed at the ATM 106, the user may be authenticated responsive to detecting the presence of the user in the ATM area 402 and/or in the drive-through area 404. For example, the user may be authenticated via license plate recognition when the car is parked in front of the ATM machine, via NFC detection of the user device 120, etc. as described herein below. Advantageously, when the user arrives at the ATM 106, their license plate is recognized, their user device 120 is detected, or the like and the ATM 106 completes the transaction without further interaction from the user as described herein below.

If the user authentication information provided at 516 matches the known and verified user authentication information, the user of the user device 120 is authenticated. If the user authentication information provided at 516 does not match the known and verified user authentication information, the user of the user device 120 is not authenticated, and the method 500 ends. The description of the method 500 continues for the situation in which the user is authenticated. The financial institution computing system 104 transmits the authentication decision to the user device 120 at 520. As discussed above, the authentication decision indicates that the user of the user device 120 is authenticated.

After receiving the user authentication decision at 520, the user device 120 renders the ATM pre-stage interface at 522. The ATM pre-stage interface is presented via the display 210 of the user device 120. In some arrangements, the ATM pre-stage interface is substantially the same interface the user would experience at the ATM 106 but reformatted to fit the display 210 and capabilities of the user device 120. The ATM pre-stage interface presents different options and transaction types for the user to select based on the transaction type (e.g., deposit funds, withdraw funds, transfers, account balance, account statement, charity donation, direct deposit advance, etc.). As described above, the ATM pre-stage interface may relate to an interface that allows the user to remotely initiate (i.e., pre-stage) a transaction for execution by an ATM 106 associated with the financial institution 102. For example, the user may initiate or pre-stage a transaction while the user waits in line for an ATM 106. In arrangements where the user is accessing the ATM pre-stage interface from a vehicle, the interface may be an audio interface presented over the vehicle's audio system.

For example, the user may want to withdraw funds from an ATM. Accordingly, the user selects, via a link, button, icon, graphic, etc. of the ATM pre-stage interface, the transaction type “withdraw funds”. The user can the select an account and an amount of funds to withdraw from the account via the ATM pre-stage interface. For example, the user may select account “0001,” corresponding to the user's checking account and enter a funds amount of $100 via the ATM pre-stage interface.

Accordingly, the user device 120 receives transaction information from the user and transmits the transaction information to the financial institution computing system 104 at 524. As described above, the user can enter transaction information into the user device 120 via the ATM pre-stage interface. Upon selection of a button, link, etc. such as “Enter”, “Submit”, or “Continue” to otherwise indicate the user's submission of the requested transaction data, the user device 120 generates a remote transaction request including the transaction information (e.g., transaction type, account number, amount of funds, etc.). The user device transmits the transaction information to the financial institution computing system 104. The transaction information may be included in a transaction request message generated by the user device 120 (e.g., via the ATM transaction circuit 216).

The financial institution computing system 104 receives the transaction information, validates the transaction information, and queues the transaction for completion at 526. The transaction information may be packaged as part of a transaction request message received from the user device 120. In some arrangements, the financial institution computing system 104 stores the transaction request message in memory, a database, etc. The transaction information is validated by the financial institution computing system 104 to ensure that the user has the appropriate funds available to complete the transaction and that the transaction is within a range of accepted transactions (e.g., within the ATM withdrawal limit). If the transaction information is validated, an initiated transaction is generated and queued by the financial institution computing system 104. The financial institution computing system 104 may generate a transaction identifier (e.g., a transaction number) and store the transaction information in a database (e.g., the ATM database 116) for later retrieval and completion. The transactions in the transaction queue are transactions remotely initiated (e.g., by user devices) that require completion at an ATM 106.

The financial institution computing system 104 generates and transmits a transaction code to the user device 120 at 528. The transaction code is used by the user of the user device 120 to retrieve the initiated transaction and to complete the transaction at an ATM 106. For example, the transaction code may be a one-time passcode, a QR code, a digital token transmitted via NFC to the ATM 106, etc. When the user approaches the ATM 106 to complete the initiated transaction, the user provides the transaction code to the ATM 106 (e.g., by entering the one-time passcode via the keypad of the ATM 106, by presenting a QR code on the display 210 of the user device 120 for scanning via a scanner of the ATM 106, by tapping the user device 120 to transmit a token via NFC to the ATM 106, etc. In some arrangements, a transaction code is not needed and the transaction is linked to the user's account (e.g., to the user's debit card). In such arrangements, the user can authenticate himself to the ATM 106 by dipping, swiping, or otherwise providing his debit account number to the ATM and entering his PIN. Once authenticated, the user can be presented with a listing of available initiated and not yet completed transactions to complete. In these arrangements, the method skips from 526 to 536.

After receiving the transaction code at 530, the user can go to an ATM 106 associated with the financial institution 102 to complete the transaction. In order to complete the remote transaction request, the financial institution 102 ensures that the user is paired to the correct queued transaction request. Accordingly, the method 500 continues when the user device 120 provides the transaction code and authentication information to the ATM 106 at 532. The ATM 106 receives the transaction code at 534. In some arrangements, the ATM 106 scans a code (e.g., a barcode, a QR code, etc.) displayed on the display 210 of the user device 120. In some arrangements, the user manually keys in the transaction code via an input device (e.g., a key, key pad, etc.) mounted on or configured within the ATM 106.

Alternatively, the user does not enter transaction information in order to complete the pre-staged transaction. The user interactions at the ATM 106 consists of establishing a wireless connection between the user device and the ATM and retrieving funds dispensed by the ATM. In such arrangements, the ATM 106 receives a digital code (e.g., a token, a data packet, etc.) via a wireless data connection between the ATM 106 and the user device 120 (e.g., a NFC data connection, a Bluetooth data connection, etc.). For example, the user may tap the user device 120 (e.g., a smartphone) on a surface of the ATM 106. Advantageously, user does not have to first enter transaction information to complete the transaction. For example, the user does not enter transaction information via the keypad of the ATM 106 or other input devices mounted on, configured within, or otherwise associated with the ATM 106 (e.g., audio receiver, touch display, etc.). After establishing the wireless data connection between the ATM 106 and the user device 120, the ATM 106 automatically completes the transaction by dispensing funds, receiving funds (e.g., in a deposit transaction), printing a receipt, displaying an account balance, transferring funds, and the like as described herein below at 538.

Based on the received transaction code, the ATM 106 retrieves transaction information from the financial institution computing system 104. The transaction information includes the types of accounts associated with the transaction, the transaction type, funds amount, or a combination thereof. In some arrangements, the ATM 106 sends a request with the transaction code to the financial institution computing system 104 to retrieve the transaction information. In such arrangements, the financial institution computing system 104 cross-references the ATM database 116 and provides the transaction information corresponding to the initiated or pre-staged ATM transaction. In other arrangements, the ATM 106 directly accesses the ATM database 116 to pull the transaction information corresponding to the initiated or pre-staged ATM transaction.

In some arrangements, the financial institution computing system 104 can push the transaction information to the ATM 106 automatically based, in part, on the position of the user. For example, the financial institution computing system can push the transaction information to the ATM 106 when the financial institution computing system 104 determines that the user is at, or near, the ATM 106 based on position data received from the user device 120. In a further example, the financial institution computing system 104 can push the transaction information to the ATM 106 when the user is determined to be at the ATM based on information gathered from an audio and/or video surveillance device near the ATM 106. The surveillance device may be positioned within the ATM 106, in the ATM area, and/or in the drive-through area. In some arrangements, the surveillance device may be configured to recognize a user based on an algorithm configured for license plate recognition, biometric recognition (e.g., facial, finger, eye, hand, voice, etc. recognition associated with a particular user), etc. For example, as a vehicle of a user enters the drive-through, the license plate may be captured by the surveillance device. The financial institution computing system 104 may then determine whether the license plate identifier matches stored license plate identifiers or is otherwise associated with an account or transaction of a user. Upon identifying a match of the license plate, the financial institution computing system 104 may push the transaction information to the ATM 106.

In further arrangements, the financial institution computing system 104 can automatically push the transaction information to the ATM 106 after the user is authenticated at the ATM 106. For example, the user can authenticate himself at the ATM via a biometric recognition (e.g., a facial recognition), via inserting his debit card and providing a PIN, and the like. If authenticated, the financial computing system 104 can then identify initiated transactions associated with the user and automatically push the associated transaction information to the ATM 106.

After the ATM 106 receives the transaction information, the ATM 106 completes the transaction at 538. For example, with reference to the above example including the transaction type “withdraw funds,” the ATM 106 dispenses the funds amount (e.g., $100) requested by the user in the pre-staged ATM transaction request. In other examples, the ATM 106 can complete the transaction by receiving funds (e.g., in a deposit), printing a receipt, displaying an account balance, transferring funds, and the like.

The embodiments described herein have been described with reference to drawings. The drawings illustrate certain details of specific embodiments that implement the systems, methods and programs described herein. However, describing the embodiments with drawings should not be construed as imposing on the disclosure any limitations that may be present in the drawings.

It should be understood that no claim element herein is to be construed under the provisions of 35 U.S.C. § 112(f), unless the element is expressly recited using the phrase “means for.”

As used herein, the term “circuit” may include hardware structured to execute the functions described herein. In some embodiments, each respective “circuit” may include machine-readable media for configuring the hardware to execute the functions described herein. The circuit may be embodied as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, a circuit may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOCs) circuits, etc.), telecommunication circuits, hybrid circuits, and any other type of “circuit.” In this regard, the “circuit” may include any type of component for accomplishing or facilitating achievement of the operations described herein. For example, a circuit as described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, and so on).

The “circuit” may also include one or more processors communicatively coupled to one or more memory or memory devices. In this regard, the one or more processors may execute instructions stored in the memory or may execute instructions otherwise accessible to the one or more processors. In some embodiments, the one or more processors may be embodied in various ways. The one or more processors may be constructed in a manner sufficient to perform at least the operations described herein. In some embodiments, the one or more processors may be shared by multiple circuits (e.g., circuit A and circuit B may comprise or otherwise share the same processor which, in some example embodiments, may execute instructions stored, or otherwise accessed, via different areas of memory). Alternatively or additionally, the one or more processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors. In other example embodiments, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multi-threaded instruction execution. Each processor may be implemented as one or more general-purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components structured to execute instructions provided by memory. The one or more processors may take the form of a single core processor, multi-core processor (e.g., a dual core processor, triple core processor, quad core processor, etc.), microprocessor, etc. In some embodiments, the one or more processors may be external to the apparatus, for example the one or more processors may be a remote processor (e.g., a cloud based processor). Alternatively or additionally, the one or more processors may be internal and/or local to the apparatus. In this regard, a given circuit or components thereof may be disposed locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud based server). To that end, a “circuit” as described herein may include components that are distributed across one or more locations.

An example system for implementing the overall system or portions of the embodiments might include a general purpose computing computers in the form of computers, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. Each memory device may include non-transient volatile storage media, non-volatile storage media, non-transitory storage media (e.g., one or more volatile and/or non-volatile memories), etc. In some embodiments, the non-volatile media may take the form of ROM, flash memory (e.g., flash memory such as NAND, 3D NAND, NOR, 3D NOR, etc.), EEPROM, MRAM, magnetic storage, hard discs, optical discs, etc. In other embodiments, the volatile storage media may take the form of RAM, TRAM, ZRAM, etc. Combinations of the above are also included within the scope of machine-readable media. In this regard, machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions. Each respective memory device may be operable to maintain or otherwise store information relating to the operations performed by one or more associated circuits, including processor instructions and related data (e.g., database components, object code components, script components, etc.), in accordance with the example embodiments described herein.

It should also be noted that the term “input devices,” as described herein, may include any type of input device including, but not limited to, a keyboard, a keypad, a mouse, joystick or other input devices performing a similar function. Comparatively, the term “output device,” as described herein, may include any type of output device including, but not limited to, a computer monitor, printer, facsimile machine, or other output devices performing a similar function.

Any foregoing references to currency or funds are intended to include fiat currencies, non-fiat currencies (e.g., precious metals), and math-based currencies (often referred to as cryptocurrencies). Examples of math-based currencies include Bitcoin, Litecoin, Dogecoin, and the like.

It should be noted that although the diagrams herein may show a specific order and composition of method steps, it is understood that the order of these steps may differ from what is depicted. For example, two or more steps may be performed concurrently or with partial concurrence. Also, some method steps that are performed as discrete steps may be combined, steps being performed as a combined step may be separated into discrete steps, the sequence of certain processes may be reversed or otherwise varied, and the nature or number of discrete processes may be altered or varied. The order or sequence of any element or apparatus may be varied or substituted according to alternative embodiments. Accordingly, all such modifications are intended to be included within the scope of the present disclosure as defined in the appended claims. Such variations will depend on the machine-readable media and hardware systems chosen and on designer choice. It is understood that all such variations are within the scope of the disclosure. Likewise, software and web implementations of the present disclosure could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from this disclosure. The embodiments were chosen and described in order to explain the principals of the disclosure and its practical application to enable one skilled in the art to utilize the various embodiments and with various modifications as are suited to the particular use contemplated. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the present disclosure as expressed in the appended claims. 

What is claimed is:
 1. A system comprising: a location identifier device configured to transmit a beacon identifier to a user device when the user device is within a predetermined range of an area and receive location information from the user device associated with a user; a surveillance device configured to capture video surveillance from the area; and a computer system comprising a processor and a memory, the computer system configured to: receive the location information from the user device via the location identifier device; receive a request for an automated teller machine (ATM) transaction from the user device, the request including attribute information associated with the user; obtain, from the received video surveillance, captured attribute information associated with the user comprising a license plate of a vehicle in the area; determine that the captured attribute information at least partially matches the attribute information from the request; identify, based on the captured attribute information at least partially matching the attribute information from the request, the user associated with the request; transmit a transaction code to the user device based on (i) the location information from the user device being within the area, (ii) the captured attribute information at least partially matching the attribute information from the request, and (iii) the identification of the user associated with the request; receive the transaction code from the user device via an ATM within the area; and facilitate the ATM transaction at the ATM based at least partially on the received transaction code from the user device.
 2. The system of claim 1, wherein the computer system is further configured to generate the transaction code.
 3. The system of claim 1, wherein the computer system is further configured to: store the attribute information from the request in a customer database by associating the attribute information with account information of the user.
 4. The system of claim 1, wherein the beacon identifier is configured to trigger the user device to transmit location information from the user device.
 5. The system of claim 1, wherein the transaction code is a barcode or a QR code.
 6. The system of claim 1, wherein the transaction code is received by the ATM via a near-field communication (NFC) tap between the user device and the ATM.
 7. The system of claim 1, wherein the request for the ATM transaction further includes transaction information regarding the ATM transaction, the transaction information including a transaction type, an account number, or an amount of funds.
 8. The system of claim 1, wherein the computer system is further configured to: provide, based on the location information from the user device being within the area, an ATM interface for display on the user device; and receive, from the user device via the ATM interface, transaction information regarding the ATM transaction, the transaction information including at least one of a transaction type, an account number, or an amount of funds.
 9. A method of remotely initiating a transaction at an automated teller machine (ATM), the method comprising: receiving, from a user device associated with a user, a request for an ATM transaction, the request including attribute information associated with the user; obtaining, from a surveillance device configured to capture surveillance information regarding an area, captured attribute information of the user comprising a license plate of a vehicle in the area; determining that the captured attribute information at least partially matches the attribute information from the request; identifying, based on the captured attribute information at least partially matching the attribute information from the request, the user associated with the request; receiving location information from the user device based on a beacon identifier transmitted to the user device when the user device is within a predetermined range of the area; transmitting a transaction code to the user device based on (i) the location information from the user device being within the area, (ii) the captured attribute information at least partially matching the attribute information from the request, and (iii) the identification of the user associated with the request; receiving, from the user device via an ATM, the transaction code; and facilitating the ATM transaction at the ATM based at least partially on the received transaction code.
 10. The method of claim 9, further comprising: rendering, based on the user device being within the area, an ATM interface on a display of the user device.
 11. The method of claim 10, wherein the ATM interface comprises an audio interface presented over an audio system of the vehicle.
 12. The method of claim 9, further comprising storing the attribute information from the request in a customer database by associating the attribute information with account information of the user.
 13. A method of remotely initiating an automated teller machine (ATM) transaction, the method comprising: receiving surveillance information from a surveillance device configured to capture surveillance information regarding an area; receiving a request to initiate an ATM transaction from a user device associated with a user, the request including attribute information associated with the user; authenticating the user for the ATM transaction by: obtaining location information from the user device based on a beacon identifier transmitted to the user device when the user device is within a predetermined range of the area; obtaining, from the received surveillance information, captured attribute information of associated with the user comprising a license plate of a vehicle in the area; determining that the captured attribute information at least partially matches the attribute information of the request; identifying, based on the captured attribute information at least partially matching the attribute information from the request, the user associated with the request; and determining, based on the location information from the user device, that the user device is within the area; in response to authenticating the user, transmitting a transaction code to the user device; receiving, from the user device via an ATM within the area, the transaction code; facilitating, based on the transaction code received from the user device, the ATM transaction at the ATM.
 14. The method of claim 13, wherein the transaction code is at least one of a QR code or a barcode.
 15. The method of claim 13, wherein the transaction code is received by the ATM via a near-field communication (NFC) tap between the user device and the ATM.
 16. The method of claim 13, wherein the request further includes transaction information regarding the ATM transaction, the transaction information including a transaction type, an account number, or an amount of funds.
 17. The method of claim 13, wherein the method further comprises: providing, based on the location information from the user device being within the area, an ATM interface for display on the user device; and receiving, from the user device via the ATM interface, transaction information regarding the ATM transaction, the transaction information including at least one of a transaction type, an account number, or an amount of funds. 